redocly logoAPI docs by Redocly

Label-wise API (1.0.0)

Download OpenAPI specification:Download

E-mail: support@label-wise.nl URL: https://app.label-wise.nl

Official API documentation for the Label-wise platform. All endpoints are available via triggers.

Project

Step 1 — Create and manage Label-wise projects.

Full integration flow:

  1. Project — create project → project_id + object_id
  2. Construction — create constructions → construction_id
  3. Geometry — create rekenzone → rekenzone_id
  4. Geometry — create hoofdvlak → hoofdvlak_id (links rekenzone_id + construction_id)
  5. Geometry — create deelvlak (links hoofdvlak_id + construction_id)
  6. Dossier — upload files/photos, optionally link to a surface or construction via data_id

Create new project

Creates a new Label-wise project, including client (opdrachtgever) and object details. Returns IDs for the created records and a redirect URL to the project in Label-wise.

Authorizations:
BearerAuth
Request Body schema: application/json
required
woningbouw_basis_vakbekwaamheidsnummer
required
string

EP advisor license number — residential (woningbouw basis)

utiliteit_basis_vakbekwaamheidsnummer
string

EP advisor license number — utility (utiliteit basis)

objecttype
required
string

Object type (see Enums → ObjectType)

bouwfase
required
string

Building phase (see Enums → BuildingPhase)

opname
required
string

Survey type (option set value)

opdrachtgever_voornaam
string

Client first name

opdrachtgever_achternaam
string

Client last name

opdrachtgever_email
string

Client email address

opdrachtgever_bedrijf
string

Client company name

opdrachtgever_telefoonnummer
string

Client phone number

object_adres_huisnummer
number

House number

object_adres_huisnummertoevoeging
string

House number addition (e.g. A, bis)

object_adres_postcode
string

Postal code

object_adres_straat
string

Street name

object_adres_woonplaats
string

City

gebouwhoogte
number

Building height (meters)

projectnaam
required
string

Project name

naam_integratie_partner
required
string

Integration partner name

Responses

Request samples

Content type
application/json
{
  • "woningbouw_basis_vakbekwaamheidsnummer": "string",
  • "utiliteit_basis_vakbekwaamheidsnummer": "string",
  • "objecttype": "string",
  • "bouwfase": "string",
  • "opname": "string",
  • "opdrachtgever_voornaam": "string",
  • "opdrachtgever_achternaam": "string",
  • "opdrachtgever_email": "string",
  • "opdrachtgever_bedrijf": "string",
  • "opdrachtgever_telefoonnummer": "string",
  • "object_adres_huisnummer": 0,
  • "object_adres_huisnummertoevoeging": "string",
  • "object_adres_postcode": "string",
  • "object_adres_straat": "string",
  • "object_adres_woonplaats": "string",
  • "gebouwhoogte": 0,
  • "projectnaam": "string",
  • "naam_integratie_partner": "string"
}

Response samples

Content type
application/json
{
  • "status": "string",
  • "response": {
    }
}

Retrieve object dossier

Retrieves the dossier file and metadata for a specific object, identified by object_id. Optionally pass the EP advisor license numbers to filter by advisor.

Authorizations:
BearerAuth
query Parameters
object_id
required
string

The unique identifier of the object

woningbouw_basis_vakbekwaamheidsnummer
string

EP advisor license number for residential construction (woningbouw basis)

utiliteit_basis_vakbekwaamheidsnummer
string

EP advisor license number for utility construction (utiliteit basis)

Responses

Response samples

Content type
application/json
{
  • "status": "string",
  • "response": {
    }
}

Construction

Step 2 — Define constructions before creating geometry.

Each geometry surface (hoofdvlak/deelvlak) must be linked to a construction_id. Create all the constructions you need first, then proceed to Geometry.

Create construction

Creates a new construction record within a project.

Step 2 of 5 — create constructions before creating geometry.

The construction_id returned here is required when creating hoofdvlakken and deelvlakken. Create all constructions you need before proceeding to the Geometry steps.

Full flow:

  1. Create project → project_id
  2. Create construction → construction_id
  3. Create rekenzone → rekenzone_id
  4. Create hoofdvlak → link rekenzone_id + construction_id
  5. Create deelvlak → link hoofdvlak_id + construction_id
Authorizations:
BearerAuth
Request Body schema: application/json
required
project_id
required
string

ID of the project this construction belongs to (from create_new_lbwise_project)

naam
required
string

Name of the construction

constructie_type
required
string

Construction type (see Enums → ConstructionType)

bouwjaar
string

Construction building year (see Enums → ConstructionBuildingYear)

glas
string

Glass type (see Enums → GlassType)

kozijn
string

Frame type (see Enums → FrameType)

isolatie_aanwezig
string

Insulation present (see Enums → InsulationConstructionType)

isolatiedikte
number

Insulation thickness (mm)

isolatiedikte_onbekend
boolean

Set to true if insulation thickness is unknown

spouw_aanwezig
boolean

Cavity wall present

rieten_dak
boolean

Thatched (reed) roof

rietdikte
string

Reed thickness (see Enums → ReedThickness)

oppervlakte_beglazing
number

Glazing surface area (m²)

omtrek_beglazing
number

Glazing perimeter (m)

oppervlakte_kozijn
number

Frame surface area (m²)

psi_glas
number

Psi glass value (W/mK)

opmerkingen
string

Remarks

woningbouw_basis_vakbekwaamheidsnummer
required
string

EP advisor license number — residential (woningbouw basis)

utiliteit_basis_vakbekwaamheidsnummer
string

EP advisor license number — utility (utiliteit basis)

naam_integratie_partner
required
string

Integration partner name

Responses

Request samples

Content type
application/json
{
  • "project_id": "string",
  • "naam": "string",
  • "constructie_type": "string",
  • "bouwjaar": "string",
  • "glas": "string",
  • "kozijn": "string",
  • "isolatie_aanwezig": "string",
  • "isolatiedikte": 0,
  • "isolatiedikte_onbekend": true,
  • "spouw_aanwezig": true,
  • "rieten_dak": true,
  • "rietdikte": "string",
  • "oppervlakte_beglazing": 0,
  • "omtrek_beglazing": 0,
  • "oppervlakte_kozijn": 0,
  • "psi_glas": 0,
  • "opmerkingen": "string",
  • "woningbouw_basis_vakbekwaamheidsnummer": "string",
  • "utiliteit_basis_vakbekwaamheidsnummer": "string",
  • "naam_integratie_partner": "string"
}

Response samples

Content type
application/json
{
  • "status": "string",
  • "response": {
    }
}

Geometry

Steps 3–5 — Build the geometric structure of the object.

Geometry is hierarchical — create in this exact order:

Object
└── Rekenzone      (step 3 — linked to object via object_id)
    └── Hoofdvlak  (step 4 — linked to rekenzone_id + constructie_id)
        └── Deelvlak (step 5 — linked to hoofdvlak_id + constructie_id)

Create calculation zone

Step 3 of 5 — Creates a new calculation zone (rekenzone) linked to an object.

The rekenzone ID returned here is required when creating hoofdvlakken in step 4.

Full flow:

  1. Create project → project_id + object_id
  2. Create construction → construction_id
  3. Create calculation zone → rekenzone
  4. Create hoofdvlak → link rekenzone + construction_id
  5. Create deelvlak → link hoofdvlak + construction_id
Authorizations:
BearerAuth
Request Body schema: application/json
required
object_id
required
string

Object ID (returned by create_new_lbwise_project)

naam_rekenzone
required
string

Name of the calculation zone

woningbouw_basis_vakbekwaamheidsnummer
required
string

EP advisor license number — residential (woningbouw basis)

utiliteit_basis_vakbekwaamheidsnummer
string

EP advisor license number — utility (utiliteit basis)

naam_integratie_partner
required
string

Integration partner name

Responses

Request samples

Content type
application/json
{
  • "object_id": "string",
  • "naam_rekenzone": "string",
  • "woningbouw_basis_vakbekwaamheidsnummer": "string",
  • "utiliteit_basis_vakbekwaamheidsnummer": "string",
  • "naam_integratie_partner": "string"
}

Response samples

Content type
application/json
{
  • "status": "string",
  • "response": {
    }
}

Create main surface

Step 4 of 5 — Creates a main surface (hoofdvlak) within a calculation zone.

Requires rekenzone_id (step 3) and constructie_id (step 2). The hoofdvlak ID returned here is required when creating deelvlakken in step 5.

Authorizations:
BearerAuth
Request Body schema: application/json
required
rekenzone_id
required
string

Calculation zone ID from create_calculation_zone

constructie_id
required
string

Construction ID from create_construction

naam_hoofdvlak
required
string

Name of the main surface

locatie
required
string

Surface location (see Enums → MainSurfaceLocation)

oppervlak
required
number

Surface area (m²)

hellingshoek
required
string

Slope angle (see Enums → SlopeType)

grenst_aan
required
string

Borders (see Enums → BorderType)

orientatie
string

Orientation (see Enums → OrientationType)

breedte
number

Width (m)

hoogte
number

Height (m)

bodemisolatie_kruipruimte
string

Crawl space floor insulation (see Enums → CrawlSpaceFloorInsulation)

vloer_onder_maaiveld
boolean

Floor below ground level

diepte_vloer_onder_maaiveld
number

Depth of floor below ground level (m)

perimeter
number

Perimeter (m)

woningbouw_basis_vakbekwaamheidsnummer
required
string

EP advisor license number — residential (woningbouw basis)

utiliteit_basis_vakbekwaamheidsnummer
string

EP advisor license number — utility (utiliteit basis)

naam_integratie_partner
required
string

Integration partner name

Responses

Request samples

Content type
application/json
{
  • "rekenzone_id": "string",
  • "constructie_id": "string",
  • "naam_hoofdvlak": "string",
  • "locatie": "string",
  • "oppervlak": 0,
  • "hellingshoek": "string",
  • "grenst_aan": "string",
  • "orientatie": "string",
  • "breedte": 0,
  • "hoogte": 0,
  • "bodemisolatie_kruipruimte": "string",
  • "vloer_onder_maaiveld": true,
  • "diepte_vloer_onder_maaiveld": 0,
  • "perimeter": 0,
  • "woningbouw_basis_vakbekwaamheidsnummer": "string",
  • "utiliteit_basis_vakbekwaamheidsnummer": "string",
  • "naam_integratie_partner": "string"
}

Response samples

Content type
application/json
{
  • "status": "string",
  • "response": {
    }
}

Create sub-surface

Step 5 of 5 — Creates a sub-surface (deelvlak) within a main surface.

Requires hoofdvlak_id (step 4) and constructie_id (step 2).

Authorizations:
BearerAuth
Request Body schema: application/json
required
hoofdvlak_id
required
string

Main surface ID from create_mainplane

constructie_id
required
string

Construction ID from create_construction

naam_deelvlak
required
string

Name of the sub-surface

oppervlak
required
number

Surface area (m²)

orientatie
required
string

Orientation (see Enums → OrientationType)

hellingshoek
required
string

Slope angle (see Enums → SlopeType)

aantal
required
number

Number of sub-surfaces of this type

breedte
number

Width (m)

hoogte
number

Height (m)

woningbouw_basis_vakbekwaamheidsnummer
required
string

EP advisor license number — residential (woningbouw basis)

utiliteit_basis_vakbekwaamheidsnummer
string

EP advisor license number — utility (utiliteit basis)

naam_integratie_partner
required
string

Integration partner name

Responses

Request samples

Content type
application/json
{
  • "hoofdvlak_id": "string",
  • "constructie_id": "string",
  • "naam_deelvlak": "string",
  • "oppervlak": 0,
  • "orientatie": "string",
  • "hellingshoek": "string",
  • "aantal": 0,
  • "breedte": 0,
  • "hoogte": 0,
  • "woningbouw_basis_vakbekwaamheidsnummer": "string",
  • "utiliteit_basis_vakbekwaamheidsnummer": "string",
  • "naam_integratie_partner": "string"
}

Response samples

Content type
application/json
{
  • "status": "string",
  • "response": {
    }
}

Dossier

Step 6 — Upload files and photos to the object dossier.

Use the data_id field to associate a file or photo with a specific element:

data_id value Associates with
hoofdvlak_id A main surface (hoofdvlak)
deelvlak_id A sub-surface (deelvlak)
construction_id A construction

Leave data_id empty to attach the file to the object dossier without a specific link.

Create dossier item

Step 6 — Uploads a file or photo to the object dossier.

Use data_id to associate the item with a specific element:

data_id value Associates with
hoofdvlak_id A main surface (from create_mainplane)
deelvlak_id A sub-surface (from create_subplane)
construction_id A construction (from create_construction)

Leave data_id empty to attach the file to the object dossier without a specific link.

Authorizations:
BearerAuth
Request Body schema: application/json
required
object_id
required
string

Object ID from create_new_lbwise_project

naam
required
string

Name of the dossier item

bestand
required
string

File to upload (URL or file reference)

foto
string

Photo to upload (URL or file reference)

categorie
required
string

Category of the dossier item (see Enums → FileCategory)

type
required
string

File type (see Enums → FileType)

data_id
string

Optional — links this item to a specific element.

Pass a hoofdvlak_id, deelvlak_id, or construction_id to associate this file/photo with that element. Leave empty to attach to the object dossier only.

woningbouw_basis_vakbekwaamheidsnummer
required
string

EP advisor license number — residential (woningbouw basis)

utiliteit_basis_vakbekwaamheidsnummer
string

EP advisor license number — utility (utiliteit basis)

naam_integratie_partner
required
string

Integration partner name

Responses

Response Schema: application/json
status
string

Outcome of the request

object

Request samples

Content type
application/json
{
  • "object_id": "string",
  • "naam": "string",
  • "bestand": "string",
  • "foto": "string",
  • "categorie": "string",
  • "type": "string",
  • "data_id": "string",
  • "woningbouw_basis_vakbekwaamheidsnummer": "string",
  • "utiliteit_basis_vakbekwaamheidsnummer": "string",
  • "naam_integratie_partner": "string"
}

Response samples

Content type
application/json
{
  • "status": "string",
  • "response": {
    }
}

Enums

Geometry-focused enum values — option sets for construction types, surface properties, shading, and more.

Retrieve geometry enum values

Retrieves geometry-specific enum values used within the Label-wise platform. Returns option sets for building types, construction types, surface properties, shading, and more.

Authorizations:
BearerAuth

Responses

Response Schema: application/json
status
string

Outcome of the request

object
BorderType
Array of strings

Available values for BorderType

ObjectType
Array of strings

Available values for ObjectType

BuildingSubtype
Array of strings

Available values for BuildingSubtype

Buildingtype
Array of strings

Available values for Buildingtype

BuildIntegrationVentilationType
Array of strings

Available values for BuildIntegrationVentilationType

ConstantObstruction
Array of strings

Available values for ConstantObstruction

ConstructionBuildingYear
Array of strings

Available values for ConstructionBuildingYear

ConstructionInputType
Array of strings

Available values for ConstructionInputType

ConstructionType
Array of strings

Available values for ConstructionType

CrawlSpaceFloorInsulation
Array of strings

Available values for CrawlSpaceFloorInsulation

DaylightControlType
Array of strings

Available values for DaylightControlType

EnergyLabel
Array of strings

Available values for EnergyLabel

FileType
Array of strings

Available values for FileType

FloorConstructionType
Array of strings

Available values for FloorConstructionType

FrameType
Array of strings

Available values for FrameType

GlassType
Array of strings

Available values for GlassType

InsulationConstructionType
Array of strings

Available values for InsulationConstructionType

IntakeType
Array of strings

Available values for IntakeType

LateralObstruction
Array of strings

Available values for LateralObstruction

LocationInBuilding
Array of strings

Available values for LocationInBuilding

MainSurfaceLocation
Array of strings

Available values for MainSurfaceLocation

OrientationType
Array of strings

Available values for OrientationType

OverhangInput
Array of strings

Available values for OverhangInput

RecordType
Array of strings

Available values for RecordType

ReedThickness
Array of strings

Available values for ReedThickness

RelativeObstruction
Array of strings

Available values for RelativeObstruction

RoofType
Array of strings

Available values for RoofType

ShadingColor
Array of strings

Available values for ShadingColor

ShadingInput
Array of strings

Available values for ShadingInput

SlopeType
Array of strings

Available values for SlopeType

SolarShading
Array of strings

Available values for SolarShading

ShadingObstruction
Array of strings

Available values for ShadingObstruction

SunShading
Array of strings

Available values for SunShading

WallConstructionType
Array of strings

Available values for WallConstructionType

BuildingPhase
Array of strings

Available values for BuildingPhase

ObjectEnergyLabel
Array of strings

Available values for ObjectEnergyLabel

FileCategory
Array of strings

Available values for FileCategory

Response samples

Content type
application/json
{
  • "status": "string",
  • "response": {
    }
}